picocrypt-ng: Add version 2.12#17903
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis PR adds a new Scoop Extras package manifest for Picocrypt-NG v2.12. The manifest includes version, description, homepage, GPL-3.0-or-later license, two 64-bit artifacts (portable and CLI) with targets and SHA-256 hashes, a "Picocrypt NG" shortcut, and autoupdate entries using GitHub release download URLs plus GitHub tag API-based hash discovery. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
bucket/picocrypt-ng.json (1)
1-26: Run local manifest validation before merge.Please verify with:
scoop config debug true scoop config gh_token <your-github-token> # read-only token .\bin\checkver.ps1 -App picocrypt-ng -f .\bin\formatjson.ps1 -App picocrypt-ng scoop install bucket\picocrypt-ng.json -a 64bitIf any checklist ambiguity comes up, use:
- https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md
- https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests
As per coding guidelines: “Provide clear instructions for testing the manifest locally before submission” and include contribution/wiki links for guidance.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@bucket/picocrypt-ng.json` around lines 1 - 26, Add clear local validation and testing steps for the picocrypt-ng manifest (picocrypt-ng.json) to your PR description or a CONTRIBUTING note: list the exact commands to run (enable debug, set GH token, run .\bin\checkver.ps1 -App picocrypt-ng -f, .\bin\formatjson.ps1 -App picocrypt-ng, and scoop install bucket\picocrypt-ng.json -a 64bit), and include links to the Scoop contribution and manifest wiki pages for guidance (ScoopInstaller/.github CONTRIBUTING.md and Scoop Wiki App-Manifests). This ensures reviewers can reproduce manifest validation before merge; update the PR text (not the JSON fields) to contain those commands and links.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@bucket/picocrypt-ng.json`:
- Around line 1-26: Add clear local validation and testing steps for the
picocrypt-ng manifest (picocrypt-ng.json) to your PR description or a
CONTRIBUTING note: list the exact commands to run (enable debug, set GH token,
run .\bin\checkver.ps1 -App picocrypt-ng -f, .\bin\formatjson.ps1 -App
picocrypt-ng, and scoop install bucket\picocrypt-ng.json -a 64bit), and include
links to the Scoop contribution and manifest wiki pages for guidance
(ScoopInstaller/.github CONTRIBUTING.md and Scoop Wiki App-Manifests). This
ensures reviewers can reproduce manifest validation before merge; update the PR
text (not the JSON fields) to contain those commands and links.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 5fb45b8f-80dc-4756-b85d-457046413412
📒 Files selected for processing (1)
bucket/picocrypt-ng.json
|
/verify |
|
All changes look good. Wait for review from human collaborators. picocrypt-ng
|
|
/verify |
|
Your changes did not pass all checks. Please address the issues in the manifest and comment starting with picocrypt-ng
|
aliesbelik
left a comment
There was a problem hiding this comment.
- Guess manifest could provide cli version along with main app.
- Please update to the latest version.
Co-authored-by: Aliaksandr Belik <1752374+aliesbelik@users.noreply.github.com>
Co-authored-by: Aliaksandr Belik <1752374+aliesbelik@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@bucket/picocrypt-ng.json`:
- Line 36: The JSON contains invalid escape sequences `\(` and `\)` inside the
"find" regex string; update the string literal used in the "find" field (the
value starting with "sha256(Picocrypt-NG-portable.exe)...") to double-escape the
backslashes before the parentheses so they become `\\(` and `\\)`, e.g. change
"sha256\(Picocrypt-NG-portable.exe\)\\s+$sha256" to
"sha256\\(Picocrypt-NG-portable.exe\\)\\s+$sha256" and make the same change for
the other occurrence referenced in the comment.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 385bae56-6bda-4e65-a7ff-924a6d849fac
📒 Files selected for processing (1)
bucket/picocrypt-ng.json
There was a problem hiding this comment.
♻️ Duplicate comments (1)
bucket/picocrypt-ng.json (1)
36-36:⚠️ Potential issue | 🔴 Critical | ⚡ Quick winFix invalid JSON escaping in autoupdate hash regex.
Line 36 and Line 40 use
\(/\), which are invalid JSON escapes and make the manifest unparsable. Use\\(and\\)in JSON string literals.Also, please refer to the Scoop contribution docs for manifest formatting expectations:
- https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md
- https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests
Suggested patch
- "regex": "sha256\(Picocrypt-NG-portable.exe\)\\s+$sha256" + "regex": "sha256\\(Picocrypt-NG-portable.exe\\)\\s+$sha256" ... - "regex": "sha256\(Picocrypt-NG-cli.exe\)\\s+$sha256" + "regex": "sha256\\(Picocrypt-NG-cli.exe\\)\\s+$sha256"#!/bin/bash set -euo pipefail # 1) Verify JSON parses jq empty bucket/picocrypt-ng.json # 2) Show current regex lines for manual confirmation rg -n '"regex":' bucket/picocrypt-ng.jsonAlso applies to: 40-40
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@bucket/picocrypt-ng.json` at line 36, The "regex" string literals in picocrypt-ng.json currently contain single backslash escapes `\(` and `\)` which are invalid in JSON; update both regex values (the "regex" entries referencing sha256(Picocrypt-NG-portable.exe) and the other occurrence) to use double backslashes `\\(` and `\\)` so the JSON string contains literal parentheses in the regex, then validate the manifest parses (e.g., with jq) and re-run any manifest linting.Source: Linters/SAST tools
🧹 Nitpick comments (1)
bucket/picocrypt-ng.json (1)
1-46: Run local Scoop manifest validation steps before merge.Recommended checks for this manifest (
picocrypt-ng):scoop config debug true scoop config gh_token <your-github-token> # read-only token .\bin\checkver.ps1 -App picocrypt-ng -f .\bin\formatjson.ps1 -App picocrypt-ng scoop install bucket/picocrypt-ng.json -a 64bit🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@bucket/picocrypt-ng.json` around lines 1 - 46, Run the local Scoop manifest validation and installation checks for the manifest "picocrypt-ng" (bucket/picocrypt-ng.json): enable debug and set a GitHub read-only token, then execute the checkver and formatjson scripts for the App name "picocrypt-ng" and attempt a 64-bit install to catch autoupdate/checkver or JSON formatting issues; if any step fails, fix the manifest fields referenced in the diff (e.g., "checkver", "autoupdate", "architecture.64bit.url", "architecture.64bit.hash", "bin", "shortcuts") so checkver regexes and hashes are correct and formatjson passes, then re-run the validation until all steps succeed before merging.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@bucket/picocrypt-ng.json`:
- Line 36: The "regex" string literals in picocrypt-ng.json currently contain
single backslash escapes `\(` and `\)` which are invalid in JSON; update both
regex values (the "regex" entries referencing sha256(Picocrypt-NG-portable.exe)
and the other occurrence) to use double backslashes `\\(` and `\\)` so the JSON
string contains literal parentheses in the regex, then validate the manifest
parses (e.g., with jq) and re-run any manifest linting.
---
Nitpick comments:
In `@bucket/picocrypt-ng.json`:
- Around line 1-46: Run the local Scoop manifest validation and installation
checks for the manifest "picocrypt-ng" (bucket/picocrypt-ng.json): enable debug
and set a GitHub read-only token, then execute the checkver and formatjson
scripts for the App name "picocrypt-ng" and attempt a 64-bit install to catch
autoupdate/checkver or JSON formatting issues; if any step fails, fix the
manifest fields referenced in the diff (e.g., "checkver", "autoupdate",
"architecture.64bit.url", "architecture.64bit.hash", "bin", "shortcuts") so
checkver regexes and hashes are correct and formatjson passes, then re-run the
validation until all steps succeed before merging.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 4bb02d78-3c61-44e4-8976-e0759ca7eec1
📒 Files selected for processing (1)
bucket/picocrypt-ng.json
|
/verify |
|
Your changes did not pass all checks. Please address the issues in the manifest and comment starting with picocrypt-ng
|
|
/verify |
|
Your changes did not pass all checks. Please address the issues in the manifest and comment starting with picocrypt-ng
|
|
/verify |
|
Your changes did not pass all checks. Please address the issues in the manifest and comment starting with picocrypt-ng
|
|
/verify |
|
All changes look good. Wait for review from human collaborators. picocrypt-ng
|
|
Thanks for your review! |
Closes #17170
<manifest-name[@version]|chore>: <general summary of the pull request>